PHLEGM v8 Checkpoint 13 - Build Resolver + Identifier Length Guard
Timestamp: 2026-1007-1630-2844

Source baseline:
- PHLEGM-v8-Developer-Distribution-FB-Validator-12-2026-1007-1621-3883.zip
- PHLEGM-v8-Compiler-Logs-2026-1007-1625-1101.zip

Observed build failure:
- Checkpoint 12 successfully passed the corrected identifier validator.
- All four Windows targets then failed in Resolve-FreeBasicCompiler before invoking fbc because Build-PHLEGM-v8.ps1 called the removed helper name ConvertTo-PHLEGMArchitecture.
- The same resolver contained a second stale call, Get-PortableExecutableArchitecture, which would have failed immediately afterward.

Checkpoint 13 changes:
- Resolve-FreeBasicCompiler now calls ConvertTo-PHLEGMCanonicalArchitecture.
- Windows compiler architecture filtering now calls Get-PeArchitecture.
- Validate-FreeBasicIdentifiers.ps1 now hard-fails every identifier token longer than 128 characters because FreeBASIC truncates such identifiers.
- Identifier-length validation is lexical after string/comment removal, so it covers symbols outside the declaration parser too.
- Overlength identifiers are also checked for case-insensitive collisions after FreeBASIC's 128-character truncation.
- Existing reserved-word/record-alias behavior from Checkpoint 12 is retained.
- No emulator, graphics, host ABI, tree/archive, CHR-font, PPU/APU, FPS/FS, or backend policy code was changed.

Validation performed in this checkpoint environment:
- Compiler log bundle inspected: all four Windows failures identify ConvertTo-PHLEGMArchitecture as the first exception.
- Stale helper references: 0 ConvertTo-PHLEGMArchitecture calls; 0 Get-PortableExecutableArchitecture calls.
- Replacement helpers exist and are referenced: ConvertTo-PHLEGMCanonicalArchitecture and Get-PeArchitecture.
- Full source lexical identifier scan: 82 source files; longest identifier 44 characters; 0 identifiers over 128.
- JSON parse: PASS (14 files).
- Text newline policy: PASS (CRLF except *.sh=LF).
- bash -n: PASS for Linux shell scripts.
- pwsh/powershell and fbc are not installed in this container, so hands-on Windows compilation remains the next verification step.
